This revolves around what we think of as globality

I think being more specific with the language we refer to this as is better as original ideas are forgotten to more described aspects

currently stored data in the config store: Known stores | as LongTermStoreInterfaceInstances Manual filter list configurations | as ManualFilterLists Manual query group configurations | as ManualQueryGroups Recently chosen types | as RecentTypes Manual save group configurations | as ManualSavingGroups

This data does not specify its context It is up to the discerning body to interperet the contents of the config store A problem with that approach appears when desigining new data You could design a method of interaction that inteferes with a previous one or not

Usernames

For user configuration we could store the user name in the tag We should probably separate this from the operating systems concept of users

For now i dont see why this has to be anything other than a text entry box Storing this within the config store is simple, last entered string

also want a config option for whether we should submit personal data upon version updates.

Where this data should be stored is dependant upon how this software should be used Talking in terms of software aspects, data and synchronisation/ collaboration

Well if it organised around the individual then this could influence my decisions So I want planning around personal survival to be the focus with the ability to then combine efforts things must be modelled then to allow general work

So what would the benefits of congregating processing power to one place be? well the weaknesses include the homogonisation of decisions, the ability to combine processing to a central location but to then easily split off from that seems important this design doesnt have to be implemented right away if desired as I need to get current design for production in place Elements often have to be considered in conjunction to fit well and this is balanced with mental ability to hold these things in consideration this can be augmented by physical stores of mental models

The data of the current user is closely tied to the computer and so we could store it there

What about not maintaining them in memory and loading from the store when needed?